What

The main change here was to update the migration commands so all of them have a consistent hierarchy. Here is what they look like right now:

• db sdp migrate up | down: for sdp per-tenant migrations
  • The old command was db migrate up | down. Notice it had a different (global) hierarchy despite being a per-tenant command
• db auth migrate up | down: for auth per-tenant migrations
  • This haven't changed.
• db admin migrate up | down: for admin migrations that are relevant to registering and organizing the tenants
  • The old command was db tenant migrate up | down. It was for a global thing, yet it looked less global than the first command. Also, despite being called tenant, it had a global scope rather than per-tenant

Additional changes:

• Updated the migration folders and migration table tracker to be consistent with the command names
• Refactored the code a bit for increased consistency and better organization
• Updated wording and method documentation for increased clarity. It took me a while to figure out what each command was does, so this was highly needed especially for people who will not be debugging the code.

Why

• The commands were inconsistent
• The documentation was unclear
• In preparation for adding the tss migrations

Checklist

PR Structure

• This PR has a reasonably narrow scope (if not, break it down into smaller PRs).
• This PR title and description are clear enough for anyone to review it.
• This PR does not mix refactoring changes with feature changes (split into two PRs otherwise).

Thoroughness

• This PR adds tests for the new functionality or fixes.
• This PR contains the link to the Jira ticket it addresses.

Configs and Secrets

• No new CONFIG variables are required -OR- the new required ones were added to the helmchart's values.yaml file.
• No new CONFIG variables are required -OR- the new required ones were added to the deployments (pr-preview, dev, demo, prd).
• No new SECRETS variables are required -OR- the new required ones were mentioned in the helmchart's values.yaml file.
• No new SECRETS variables are required -OR- the new required ones were added to the deployments (pr-preview secrets, dev secrets, demo secrets, prd secrets).

Release

• This is not a breaking change.
• This is ready for production.. If your PR is not ready for production, please consider opening additional complementary PRs using this one as the base. Only merge this into develop or main after it's ready for production!

Deployment

• Does the deployment work after merging?